Advanced
Settings for Non Delivery Report (NDR) messages
SMTP / MIME
Custom HELO Remote
You can instruct Hexamail Guard to use a customized HELO line when performing SMTP communications with remote servers for sending email.
Typical uses of this is to instruct Hexamail Guard to use your domain name or host name when performing the HELO, e.g. HELO mail.example.com, where mail.example.com is the fully qualified hostname of the
server running Hexamail Guard.
Use the token <domain> to insert your primary domain automatically: HELO <domain> becomes HELO example.com when example.com is your configured primary domain.
Use the token <host> to insert the host name of your server automatically: HELO <host> becomes HELO mailserver when mailserver is your host name.
Hence, HELO <host>.<domain> becomes HELO mailserver.example.com. Alternatively use HELO mailserver.example.com directly to ensure the correct fully qualified host name is sent.
If you are trying to use Authentication with a Microsoft Exchange Server and get Send Hello first errors, set this to EHLO instead of HELO to resolve the issue.
To configure a specific domain use: HELO mydomain.com
EHLO <domain>
Custom HELO Local
You can instruct Hexamail Guard to use a customized HELO line when performing SMTP communications with the local server for delivering email.
Typical uses of this is to instruct Hexamail Guard to use your domain name or host name when performing the HELO, e.g. HELO mail.example.com, where mail.example.com is the fully qualified hostname of the
server running Hexamail Guard.
Use the token to insert your primary domain automatically: HELO becomes HELO example.com when example.com is your configured primary domain.
Use the token to insert the host name of your server automatically: HELO becomes HELO mailserver when mailserver is your host name.
Hence, HELO . becomes HELO mailserver.example.com. Alternatively use HELO mailserver.example.com directly to ensure the correct fully qualified host name is sent.
Sometimes when talking to exchange locally you need to use the local machine name alone, e.g. HELO machinename
If you are trying to use Authentication with a Microsoft Exchange Server and get Send Hello first errors, set this to EHLO instead of HELO to resolve the issue.
To configure a specific domain use: EHLO mydomain.com
To use a specific hostname use EHLO myhost.mydomain.com
EHLO <host>
Network
MaxConnections
You can use a large number of simultaneous connections to provide for large amounts of email traffic being sent. Set this high if there is lots of outgoing mail and your mail server can handle large numbers of connections simultaneously.
1 - 64
12
8
DNS Servers
You can optionally specify DNS servers to use for MX Lookups. If you do not specify anything here the default DNS servers configured on the machine on which Hexamail Guard is running will be used, or, if they are not available or configured, the standard root DNS servers are used.
NOTE: these are only used if outbound email is being sent through Hexamail Guard and MX lookup delivery is being used. If a smarthost is configured, the Smart host will perform the MX lookup and delivery and no DNS server list is required.
If you are experiencing MX Lookup errors, check your DNS settings on the machine or add your DNS server IP addresses to this list to ensure the correct DNS servers are being used.
MXFailureRetry
By default if no MX host exists for a domain hexamail will try sending to the domain name as a host inline with the SMTP RFC and
retry as per your retry schedule under the Errors settings.
If you prefer to immediately fail the email for a recipient if the MX lookup fails for a recipient select Off for this setting.
On/Off
On
Custom NDR
Displayed Name
Enter the display name you wish to use for the NDR (Non delivery report) Sender. ex: Administrator
Postmaster
Administrator
Return Sender Address
Enter the email address you wish to use for the NDR Sender. ex: postmaster@domain.com
postmaster@domain.com
